The _b_o_o_t__c_p_u_s_e_t._s_o library provides a method for putting _i_n_i_t(1M) into a
_c_p_u_s_e_t(4). Since all "standard" processes are descendents of _i_n_i_t, this
means that all standard processes on the system (daemons, interactive,
etc.) will be confined to that cpuset. The cpuset is named bbbbooooooootttt.
The _b_o_o_t__c_p_u_s_e_t._s_o library is normally installed on SGI ccNUMA systems.
If it is found in ////lllliiiibbbb33332222 by _i_n_i_t, it will be loaded and executed. The
behaviour of the library is controlled by ////eeeettttcccc////ccccoooonnnnffffiiiigggg////bbbbooooooootttt____ccccppppuuuusssseeeetttt and
////eeeettttcccc////ccccoooonnnnffffiiiigggg////bbbbooooooootttt____ccccppppuuuusssseeeetttt....ccccoooonnnnffffiiiigggg. The former file follows the _c_h_k_c_o_n_f_i_g(1M)
convention and may be manipulated by _c_h_k_c_o_n_f_i_g. If it contains the word
oooonnnn, creation of the cpuset will proceed unless an error occurs. If ooooffffffff is
found, the library will exit and normal init processing will resume. The
////eeeettttcccc////ccccoooonnnnffffiiiigggg////bbbbooooooootttt____ccccppppuuuusssseeeetttt....ccccoooonnnnffffiiiigggg file follows the syntax convention of
_c_p_u_s_e_t(4). All restrictions specified in _m_i_s_e_r__c_p_u_s_e_t(1) apply.
FFFFIIIILLLLEEEESSSS
/etc/config/boot_cpuset Follows chkconfig(1M) convention. If
ooooffffffff, no further processing occurs and
init will resume.
/etc/config/boot_cpuset.config Configuration file specifing the
cpuset. See cpuset(4) for more
information.
WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS
No attempt is made to check the configuration file for a reasonable
configuration. Specifying an unreasonable configuration may leave system
non-functional.
Note: The cpuset is not activated if the system is booted into single
user mode. This provides an escape mechanism should the configuration
prove to be unreasonable.
Processes that are moved out of a cpuset (any) will be left outside of
all cpusets and not returned to the bbbbooooooootttt cpuset. To work around this
problem, the process should reattach itself to the bbbbooooooootttt cpuset rather
than be moved it out of the source cpuset.
NNNNOOOOTTTTEEEESSSS
Allthough this mechanism can be used in a standalone fashion with the
_c_p_u_s_e_t(1) command, it is primarily intended for use by batch systems. Due
to the above noted limitation of moving processes between cpusets, it may
not practical to dynamically re-adjust resources for running processes or